Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade @apollo/client from 3.10.8 to 3.11.0 #3363

Closed

Conversation

admin-token-bot
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @apollo/client from 3.10.8 to 3.11.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 4 versions ahead of your current version.

  • The recommended version was released on 21 days ago.

Release notes
Package name: @apollo/client
  • 3.11.0 - 2024-07-22

    Potentially Breaking Fixes

    • #11789 5793301 Thanks @ phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

      This was a type bug - these errors were never GraphQLError instances
      to begin with, and the GraphQLError class has additional properties that can
      never be correctly rehydrated from a GraphQL result.
      The correct type to use here is GraphQLFormattedError.

      Similarly, please ensure to use the type FormattedExecutionResult
      instead of ExecutionResult - the non-"Formatted" versions of these types
      are for use on the server only, but don't get transported over the network.

    • #11626 228429a Thanks @ phryneas! - Call nextFetchPolicy with "variables-changed" even if there is a fetchPolicy specified.

      Previously this would only be called when the current fetchPolicy was equal to the fetchPolicy option or the option was not specified. If you use nextFetchPolicy as a function, expect to see this function called more often.

      Due to this bug, this also meant that the fetchPolicy might be reset to the initial fetchPolicy, even when you specified a nextFetchPolicy function. If you previously relied on this behavior, you will need to update your nextFetchPolicy callback function to implement this resetting behavior.

      As an example, if your code looked like the following:

      useQuery(QUERY, {
        nextFetchPolicy(currentFetchPolicy, info) {
          // your logic here
        }
      );

      Update your function to the following to reimplement the resetting behavior:

      useQuery(QUERY, {
        nextFetchPolicy(currentFetchPolicy, info) {
          if (info.reason === 'variables-changed') {
            return info.initialFetchPolicy;
          }
          // your logic here
        }
      );

    Minor Changes

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useQueryRefHandlers.

    • #11854 3812800 Thanks @ jcostello-atlassian! - Support extensions in useSubscription

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useLoadableQuery.

    • #11863 98e44f7 Thanks @ phryneas! - Reimplement useSubscription to fix rules of React violations.

    • #11869 a69327c Thanks @ phryneas! - Rewrite big parts of useQuery and useLazyQuery to be more compliant with the Rules of React and React Compiler

    • #11936 1b23337 Thanks @ jerelmiller! - Add the ability to specify a name for the client instance for use with Apollo Client Devtools. This is useful when instantiating multiple clients to identify the client instance more easily. This deprecates the connectToDevtools option in favor of a new devtools configuration.

      new ApolloClient({
        devtools: {
          enabled: true,
          name: "Test Client",
        },
      });

      This option is backwards-compatible with connectToDevtools and will be used in the absense of a devtools option.

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useBackgroundQuery.

    • #11930 a768575 Thanks @ jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending @ apollo/graphql-testing-library.

    Patch Changes

  • 3.11.0-rc.2 - 2024-07-15

    Patch Changes

    • #11951 0de03af Thanks @ phryneas! - add React 19 RC to peerDependencies

    • #11937 78332be Thanks @ phryneas! - createSchemaFetch: simulate serialized errors instead of an ApolloError instance

    • #11944 8f3d7eb Thanks @ sneyderdev! - Allow IgnoreModifier to be returned from a optimisticResponse function when inferring from a TypedDocumentNode when used with a generic argument.

    • #11954 4a6e86a Thanks @ phryneas! - Document (and deprecate) the previously undocumented errors property on the useQuery QueryResult type.

  • 3.11.0-rc.1 - 2024-07-10

    Patch Changes

  • 3.11.0-rc.0 - 2024-07-09

    Minor Changes

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useQueryRefHandlers.

    • #11854 3812800 Thanks @ jcostello-atlassian! - Support extensions in useSubscription

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useLoadableQuery.

    • #11863 98e44f7 Thanks @ phryneas! - Reimplement useSubscription to fix rules of React violations.

    • #11869 a69327c Thanks @ phryneas! - Rewrite big parts of useQuery and useLazyQuery to be more compliant with the Rules of React and React Compiler

    • #11936 1b23337 Thanks @ jerelmiller! - Add the ability to specify a name for the client instance for use with Apollo Client Devtools. This is useful when instantiating multiple clients to identify the client instance more easily. This deprecates the connectToDevtools option in favor of a new devtools configuration.

      new ApolloClient({
        devtools: {
          enabled: true,
          name: "Test Client",
        },
      });

      This option is backwards-compatible with connectToDevtools and will be used in the absense of a devtools option.

    • #11923 d88c7f8 Thanks @ jerelmiller! - Add support for subscribeToMore function to useBackgroundQuery.

    • #11789 5793301 Thanks @ phryneas! - Changes usages of the GraphQLError type to GraphQLFormattedError.

      This was a type bug - these errors were never GraphQLError instances
      to begin with, and the GraphQLError class has additional properties that can
      never be correctly rehydrated from a GraphQL result.
      The correct type to use here is GraphQLFormattedError.

      Similarly, please ensure to use the type FormattedExecutionResult
      instead of ExecutionResult - the non-"Formatted" versions of these types
      are for use on the server only, but don't get transported over the network.

    • #11930 a768575 Thanks @ jerelmiller! - Deprecates experimental schema testing utilities introduced in 3.10 in favor of recommending @ apollo/graphql-testing-library.

    Patch Changes

  • 3.10.8 - 2024-06-27

    Patch Changes

    • #11911 1f0460a Thanks @ jerelmiller! - Allow undefined to be returned from a cache.modify modifier function when a generic type argument is used.
from @apollo/client GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @apollo/client from 3.10.8 to 3.11.0.

See this package in npm:
@apollo/client

See this project in Snyk:
https://app.snyk.io/org/sandbox-2ba/project/9043c51f-3f0d-45c6-8455-b658274f2872?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

netlify bot commented Aug 13, 2024

Deploy Preview for device-sdk ready!

Name Link
🔨 Latest commit b524bf7
🔍 Latest deploy log https://app.netlify.com/sites/device-sdk/deploys/66bb1008ebd5420008a49e08
😎 Deploy Preview https://deploy-preview-3363--device-sdk.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@dacharyc
Copy link
Collaborator

Team is discussing plans for this test suite, so I'm closing Snyk-related PRs for it until we decide how we want to handle this test suite.

@dacharyc dacharyc closed this Aug 13, 2024
@dacharyc dacharyc deleted the snyk-upgrade-674c77adef57b1e7aea640956ecabcee branch August 13, 2024 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

nextFetchPolicy function is not called sometimes
4 participants